S3Drive - Timeout when uploading from Web app

When I upload a file to the Web app, after a certain time the request times out. This usually happens with large files or uploading multiple files. This is the error it produces. It's connected to a Backblaze B2 bucket.

Thanks for your report, couple questions. What is the approximate size of the file? What's your browser and underlying OS? Do you use multipart upload (available in the settings)? If not, please give it a go it might reduce chances of this happening, as it will upload file in smaller chunks. (edited)

Hi The files are approx 50MB each. The Web app is running on Windows 10 in Google Chrome (this is a work computer so I can't change this). I havent tried this, but I will give it a go and see if there's any problems.

I attempted to upload 5 files; all 5 failed, with a different error for each. File a was 273Mb File b was 117Mb File c was 17.2Mb File d was 50.6Mb File e was 71.4Mb All files are mp4 with h264 video, and I clicked and dragged them to the window. (I don't even know what a tome is :P)

Thanks for this screenshot. It is a perfect blend of errors caused by a different problems. First two are likely caused by this and apply for combination of multipart upload, drag&drop and files over 100MB: https://s3drive.canny.io/feature-requests/p/fix-drag-and-drop-on-web-for-100mb-multipart-upload We need to fix it. Last two are related to Backblaze not responding in a proper time. We will improve in that area by providing custom timeout values (higher defaults) and then implement this: https://s3drive.canny.io/feature-requests/p/upload-retry-improvements-including-timeout-4xx-5xx The middle one. Well it may sound like I was taking a nap and couldn't pick up your request... but in fact this intermittent error with Backblaze B2. They have some minor availability problems for quite a while, I've also experienced this. Feel free to reach out to them to confirm, but I don't think there is any better recourse than to try again later. https://www.reddit.com/r/backblaze/comments/17kb2yz/no_tomes_available_error_almost_every_night_b2/ == Tl;dr First two are certainly something we need to fix, middle one is Backblaze B2 issue, last two is something we can improve on, but there is only so much we could do if S3 API doesn't respond in a timely manner. (edited)